APP27 Purpose:
APP27 receives applications advertisements of their services and connection points and loads them in a local repository in memory, allowing other applications to find and connect to them.
In production configurations, there are two redundant APP27 services running in tandem; 1 in DC01 data center and 1 in DC02 data center.
The APP27 process is required by application startup only.
Only one APP27 instance is required at any time to support application startups.
APP27 Recovery
Considerations:
Stopping/Restart
Processes:
-
Use NTM Control Utility - Service Control -
Process Controller to stop/restart processes.
- Use APP27 nodes only when moving between nodes. (FireDaemon and DNS dependencies exist for APP27.)
- If moving APP27 to alternate node, Tech Services must redefine APP27 DNS IP addresses.
APP27 NTM Control
Commands:
Reload Static Services:
- Use NTM Control Utility – Service Control – Nespr – Reload Static Services.
- Select (and highlight) desired processes and right click to see and select desired options.
APP27 Troubleshooting Table:
|
APP27 Symptom |
Impacts |
Response |
|
Node Crashes Evidenced by: - In EMT, applications report lost communications to APP27 service. - In Solarwinds (and outlook), node and processes will be reported down. |
-Unless both APP27 services are down, or inaccessible for any reason, there will be no impact. If both are down, applications will not be able to start cleanly. Refer to: Server
Recovery - CMA - Nespr.docx Server Specific Recoveries. |
1) Refer to: Server Recovery - CMA -
Nespr.docx Server Specific Recoveries. 2) Restart affected FMR processes on alternate nodes. 3) Notify Management and PTT. |
APP27 Monitoring
Considerations:
There are no APP27 specific monitors outside of EMT.